Differentiated discontinuous reception based on network services

ABSTRACT

An improved discontinuous reception (DRX) mechanism is disclosed. In one embodiment, a method is disclosed comprising receiving a request to attach to a cellular network from user equipment (UE). The method then identifies a group identifier associated with the UE and determines a DRX parameter based on the group identifier. Finally, the method transmits the DRX parameter to the UE.

BACKGROUND INFORMATION

Discontinuous reception (DRX) plays an important role in optimizingthroughput and latency, and it may also factor into the thermal andbattery life of user equipment (UE). During DRX, a UE may negotiate datatransfer phases with a cellular network. During the phases where the UEdoes not expect data transmission, the UE can disable a cellulartransceiver, thus reducing power consumption and entering a low powerstate.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a cellular network providing differentiatedDRX based on network services according to an embodiment.

FIG. 2 is a call flow diagram illustrating a method for providingservice differentiated DRX according to an embodiment.

FIG. 3 is a flow diagram illustrating a method for providing servicedifferentiated DRX according to an embodiment.

FIG. 4 is a block diagram of a cellular network according to someembodiments.

FIG. 5 is a block diagram illustrating a cellular network according tosome embodiments.

FIG. 6 is a block diagram illustrating a computing device showing anexample of a client or server device used in the various embodiments ofthe disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

In the embodiments, a single shared identifier can be associated with aUE in both non-standalone (NSA) and standalone (SA) cellulararchitectures. In an embodiment, the UE can be grouped based onsubscriber profile identifier (SPID) values in an NSA environment. In anembodiment, the SPID can be used as a network slicing identifier in anNSA environment. Similarly, in an SA environment, the SPID value can beused in Single Network Slice Selection Assistance Information (S-NSSAI).In some embodiments, the value of the SPID in an NSA environment cancorrespond to a unique S-NSSAI value used in the SA environment. Thus,regardless of the network architecture used (e.g., NSA versus SA), theembodiments can group UEs or subscribers based on a unique identifier.

In an embodiment, each group of UEs can be associated with one or moreservices. The disclosure places no limit on the type of services;however, examples include Internet-of-Thing (IoT) services,smartphone/tablet services, smart sensor services, etc. In general, aservice can comprise a set of capabilities or functions supported by UE.

In the embodiments, a cellular network can associate a given group ofservices with a corresponding DRX policy. Thus, in an embodiment, thecellular network can define group-level connected mode DRX (cDRX) andidle mode DRX policies based on the services.

In an embodiment, the cellular network can adjust an idle mode DRXpolicy based on group identifiers. Thus, each unique group of UEs canutilize an independent idle mode DRX policy. In an embodiment, thecellular network can adjust idle mode DRX configurations while the UE isin radio resource control (RRC) IDLE mode in both NSA and SAenvironments. For example, the cellular network can configure users of asmartphone user group and IoT group with different idle mode DRXconfigurations. Specifically, the cellular network can configure the IoTgroup to have a very short DRX cycle to achieve low latency. Bycontrast, the cellular network can configure the smartphone user groupto have a longer DRX cycle to preserve battery life.

Similarly, in an embodiment, the cellular network can enable, disable,or adjust a cDRX policy per QoS Class Identifier (QCI) values in a givengroup. Examples of this operation include adjusting a cDRX profile toobtain a bounded latency, defining separate inactivity timers for NSAand SA networks, defining default cDRX profiles to meet key performanceindicators. For example, for smartphone users associated with acorresponding group, voice cDRX and internet gaming cDRX can be furtherdifferentiated within the group based on the QCI.

In the various embodiments, methods, devices, and computer-readablemedia are disclosed to provide differentiated DRX parameters to UE. Amobility manager may receive attach requests from UE and may identify agroup identifier associated with the UE. In one embodiment, the groupidentifier can be a Subscriber SPID or S-NSSAI. In one embodiment, groupidentifiers may be mapped to UE by mapping unique identifiers of the UEto group identifiers.

Next, the mobility manager may determine a DRX parameter based on thegroup identifier. The DRX parameter can comprise an idle-mode orconnected-mode DRX parameter. If determining a connected-mode DRXparameter, the mobility manager can further determine a QCI valueassociated with the UE. In such an embodiment, the mobility manager maydetermine the DRX parameter based on the group identifier and the QCIvalue. Finally, the mobility manager may transmit the DRX parameter tothe UE.

FIG. 1 is a block diagram of a cellular network 100 providingdifferentiated DRX based on network services according to an embodiment.

As illustrated, UE 102A-102D, 104A-104D, and 106A-106D arecommunicatively coupled to a core network 110 via a radio accessnetwork, RAN 108. No limit is placed on the type of UE in the cellularnetwork 100. As illustrated, UE 102A-102D, 104A-104D, and 106A-106D aregrouped or sliced into three groups 112, 114, and 116. In oneembodiment, the groups 112, 114, and 116 comprise groups determinedbased on the types of services required by the UE 102A-102D, 104A-104D,and 106A-106D. For example, UE in group 112 can comprise Ultra-ReliableLow Latency Communications (URLLC) devices such as autonomous vehiclecomputing devices, IoT devices, remote surgery devices, etc.; UE ingroup 114 can comprise enhanced mobile broadband (eMBB) devices such assmartphones, tablets, etc.; and UE in group 116 can comprise MassiveMachine-Type Communications (mMTC) devices such as sensors, meters, andmonitoring devices. Such groups are exemplary only, and other groupingscan be used. As discussed in more detail below, each of the UE102A-102D, 104A-104D, and 106A-106D can support DRX based on parametersreceived from the RAN 108.

In one embodiment, RAN 108 comprises a plurality of base stations. Someof these base stations can comprise 4G base stations, such as eNodeBbase stations, while others can comprise 5G base stations, such asgNodeB base stations. In one embodiment, a given UE can connect to a 4Gbase station or a 5G base station. In some embodiments, a given UE canconnect to both a 4G base station and a 5G base station in a dualconnectivity setup. In such a setup, the UE may use the 4G base stationfor control plane traffic, while the UE can use the 5G base station foruser plane traffic. In one embodiment, the UE within a single group mayuse different radio access technologies. For example, UE 102A canconnect to the RAN 108 via a 4G base station, while UE 102B can connectto the RAN 108 via a 5G base station. As such, each UE within a groupcan be providing the same services yet connecting to differing basestation types.

In alternative embodiments, the RAN 108 is communicatively coupled to acore network 110. In one embodiment, the core network 110 can comprise ahomogenous network. For example, the core network 110 can comprise anLTE core network. Alternatively, the core network 110 can comprise a 5Gcore network. In one embodiment, the core network 110 can comprise twonetworks, such as an LTE core network and a 5G core network.

As discussed above, since UE can move among both 4G and 5G basestations, such UE may transition between NSA and SA networkarchitectures. Nevertheless, the UE require the same DRX configurationsacross such networks regardless of the transition. As discussed in thefollowing methods, the embodiments provide techniques for grouping UEacross NSA and SA architectures and configured DRX parameters across thesame.

FIG. 2 is a call flow diagram illustrating a method for providingservice differentiated DRX according to an embodiment.

In step 202, method 200 can comprise establishing a radio resourcecontrol (RRC) connection between a UE and a base station (e.g., aneNodeB). In an embodiment, a 5G or 4G connection setup procedure can beimplemented. For example, in one embodiment, step 202 can include a UEissuing an RRC connection request to the base station. In response, thebase station can return an RRC connection setup message to the UE. TheUE can then transmit an RRC connection setup complete message to confirmthe connection. The specific details of an RRC connection setup are notprovided in detail herein for the sake of clarity.

In step 204, method 200 can comprise a base station issuing an attachrequest to a mobility manager such as a Mobility Management Entity (MME)or Access and Mobility Management Function (AMF). In one embodiment, theattach request comprises an attach request message included by the UE inthe RRC connection setup complete message. The attach request messagecan include various Information Element (IE) fields such as EvolvedPacket System (EPS) attach type, EPS mobile identity, UE networkcapabilities, EPS Session Management message containers, etc. Additionalfields can be included. In one embodiment, the attach request messagecan further include one or more DRX parameters. These DRX parameters cancomprise the preferred DRX settings of a given UE and can includeparameters such as an inactivity timer (the number of consecutivePDCCH-subframes for which the UE should be Active after successfullydecoding a PDCCH indicating a new transmission), a short DRX cyclelength, a long DRX cycle length, a short DRX cycle timer, an “on”duration timer, a Hybrid Automatic Repeat Request (HARQ) Round Trip Time(RTT) timer, a retransmission timer, etc. In some embodiments, the DRXparameters can comprise any other relevant DRX timers implemented by thenetwork.

In step 206, method 200 can include the mobility manager issuing anupdate location request to a subscriber management component. In someembodiments, prior to step 206, the UE may authenticate itself with thesubscriber management component. In an embodiment, the update locationrequest informs the SMC of the location of the UE and, morespecifically, the identity of the mobility manager servicing the UE. Theupdate location request message can include an International MobileSubscriber Identity (IMSI) of the UE, supported features of the mobilitymanager or UE, radio access type (RAT) details, and various other IEs.The update location request can include other fields as necessitated bythe network, and detail on such standard fields are not provided hereinfor the sake of clarity.

In step 208, method 200 can comprise the mobility manager receiving anupdate location answer. In an embodiment, the update location answer caninclude various IEs, including, but not limited to, a list of supportedfeatures, a result code, various flags, and subscription data. Theupdate location answer can include other fields as necessitated by thenetwork.

In one embodiment, the subscription data can include a group identifier.In one embodiment, the group identifier can comprise a subscriptionprofile identifier (SPID). In one embodiment, the subscription dataincludes the SPID of a given subscriber. In one embodiment, the SPID canbe stored in a RAT-Frequency-Selection-Priority-ID IE. In oneembodiment, a SPID value can be utilized if the UE establishes an RRCconnection with a 4G RAN. Alternatively, or in conjunction with theforegoing, the group identifier can comprise an s-Network SliceSelection Assistance Information (NSSAI) value. In one embodiment, aSPID value can be utilized if the UE establishes an RRC connection witha 5G RAN.

Notably, in an embodiment, the UE can be communicatively coupled toeither a 4G or 5G RAN. In one embodiment, the core network comprises a5G core network. Thus, when the UE is connected to the 4G RAN, the UE isconnected in an NSA mode while, when connected to the 5G RAN, the UE isconnected in an SA mode. In one embodiment, the SMC ensures that thevalue of the SPID and the NSSAI are the same. That is, the groupidentifier is the same for a given UE regardless of the RAN. Thus, evenas a UE transitions between NSA and SA modes, the same group identifiercan be transmitted from the SMC to the mobility manager as part of theupdate location answer.

In one embodiment, the SMC maintains a mapping of IMSI ranges to SPID(or NSSAI) values and other values such as QCI values. Although IMSIvalues are discussed, any unique identifier of a UE can be used. As oneexample, for a 15-digit IMSI, the last nine digits can be used to groupUEs (as the first six digits are used to identify the country and mobilenetwork operator). Thus, these last nine digits can further be segmentedinto finer-grained groupings. For example, the first five digits can beused to identify a grouping of UEs, while the last four digits can beused to refine the DRX parameters within a grouping.

For example, an IMSI format of 311480AAAAABBBB is provided as anexample. The digits “311” and “480” refer to the country code and mobilenetwork, respectively. The placeholder “AAAAA” refers to a grouping ofUEs (e.g., to URLLC devices or eMBB devices), while the placeholder“BBBB” further delineates a sub-group within the initial group (e.g.,eMBB devices requiring low latency vs. devices not requiring lowlatency). In one embodiment, the IMSI values are assigned by the mobilenetwork operator and thus can be deterministically applied to all UEsaccessing the network.

Although the above matching technique is applied, other techniques canbe utilized. For example, a database of IMSIs can be maintained suchthat each unique IMSI is associated with a SPID or other value (e.g.,QCI). In such an embodiment, when the SMC receives an IMSI, it canconsult a lookup table to identify the appropriate values.

Thus, after step 208, the mobility manager obtains a group identifier ofthe UE from the subscription management component. As discussed next,this group identifier can be used during session creation and ultimatelyused to established per-group DRX parameters. In one embodiment, afterstep 208, the mobility manager stores the returned group identifier andassociates the group identifier with the UE for later usage.

In step 210, method 200 can include the mobility manager issuing acreate session request to a gateway. In response, the gateway performs asession creation function in step 212.

In one embodiment, the gateway can comprise a packet gateway. In oneembodiment, the mobility manager can transmit a create session requestto a serving gateway which in turn transmits a create session request(e.g., default bearer request) to the packet gateway. In one embodiment,as part of step 212, the packet gateway authenticates the subscriber viaan Authentication Authorization Request (AAR) message sent to anauthentication component. The authentication component retrieves thesubscriber profile from the SMC, authenticates the user, and returns anAuthentication Authorization Answer (AAA) message to the packet gateway.

In step 214, as part of the session creation function, the gatewaytransmits a session establishment message to the policy manager (PM). Inone embodiment, the session establishment can comprise an IP-CAN ControlSession Procedure message. In one embodiment, the PM performs policycontrol functionality in the core network, including, but not limitedto, QoS authorization (e.g., QCI generation and bit rate determination)that decides how a certain data flow will be treated. In one embodiment,the PM communicates with the SMC to retrieve the subscriber profile. Asdiscussed above, in one embodiment, the subscriber profile may include aQCI associated with an IMSI range. Thus, in one embodiment, step 214includes transmitting the IMSI to obtain the subscriber profile anddefined QCI value. In one embodiment, PM can obtain this data viaSubscribe-Notifications-Request (SNR), andSubscribe-Notifications-Answer (SNA) messages exchanged between the PMand SMC.

In step 216, the PM returns the QCI value identified based on the IMSI.In one embodiment, the QCI value can be provided as part of an IP-CANControl Session Establishment message. In response, in step 218, thegateway can forward this QCI value to the mobility manager via, forexample, a create session response. Thus, when establishing a datasession, the mobility manager will receive the session establishmentparameters as well as the QCI value associated with a UE's IMSI. As withthe group identifier, the mobility manager can store this QCI value andassociate the QCI value with the UE. At the conclusion of step 218, themobility manager stores both a group identifier (e.g., SPID) and a QCIvalue for a given UE.

In step 220, the mobility manager generates or retrieves a DRX profilebased on the group identifier. In some embodiments, the mobility managercan additionally use the QCI value to retrieve or generate a DRXprofile. In one embodiment, the mobility manager uses the groupidentifier/QCI to query a database of DRX profiles. In this embodiment,an external database maintains an associate of group identifiers (andQCI values) to DRX parameters (described above). This external databasecan expose an application programming interface (API) to allow themobility manager to retrieve the relevant DRX parameters based on thegroup identifier and QCI value.

In step 222, the mobility manager transmits the DRX parameters to thebase station. In response, the base station updates the DRX handling forthe given UE and, in step 224, transmits the DRX parameters to the UE.In one embodiment, a base station can transmit the DRX parameters to theUE as part of an RRC reconfiguration message. In response, the UEupdates its DRX configuration (e.g., long/short timers, etc.) based onthe received configuration data.

In an optional embodiment, step 220 can be performed by the basestation. In such an embodiment, the mobility manager transmits the groupidentifier and (if applicable) the QCI to the base station, and the basestation can perform step 220, as previously discussed. In oneembodiment, a combination can be implemented. For example, when a UE isin RRC idle mode, the mobility manager can define the DRX parameters.Conversely, when the UE is in RRC connected mode, the base station maydetermine the DRX parameters.

In one embodiment, the group identifier can be used to identify orgenerate the DRX profile. In such an embodiment, the QCI value may notbe used. In such an embodiment, the UE may be in RRC idle mode. Inanother embodiment, the group identifier and QCI value can both be usedto identify the DRX profile. In such an embodiment, the UE may be in RRCconnected mode.

FIG. 3 is a flow diagram illustrating a method for providing servicedifferentiated DRX according to an embodiment.

In step 302, method 300 can comprise receiving a request to attach to acellular network from user equipment (UE).

In one embodiment, the request to attach comprises an attach requestmessage included by the UE in the RRC connection setup complete message.The attach request message can include various IE fields such as EPSattach type, EPS mobile identity, UE network capabilities, EPS SessionManagement message containers, etc. Additional fields can be included.In one embodiment, the attach request message can further include one ormore DRX parameters. These DRX parameters can comprise the preferred DRXsettings of a given UE and can include parameters such as an inactivitytimer (the number of consecutive PDCCH-subframes for which the UE shouldbe Active after successfully decoding a PDCCH indicating a newtransmission), a short DRX cycle length, a long DRX cycle length, ashort DRX cycle timer, an “on” duration timer, a HARQ RTT timer, aretransmission timer, etc. In some embodiments, the DRX parameters cancomprise any other relevant DRX timers implemented by the network.

In step 304, method 300 can comprise identifying a group identifierassociated with the UE.

In one embodiment, method 300 extracts an IMSI from the attach requestand includes the IMSI of the UE in an update location request messageissued to an SMC. In response, the SMC retrieves the group identifierbased on the IMSI and returns the IMSI to method 300. In one embodiment,the group identifier comprises one of a SPID or S-NSSAI. Details of thisoperation are provided in steps 206 and 208 of FIG. 2 , which are notrepeated herein again in detail.

In another embodiment, method 300 may maintain a mapping of IMSI valuesto group identifiers. In such an embodiment, method 300 need not obtainthe group identifier from an external computing device and may insteadretrieve the group identifier itself.

In one embodiment, the group identifier can be maintained across NSA andSA networks. Specifically, since the group identifier is keyed off of anIMSI or similar value unique to a UE, the corresponding group identifiercan be applied a UE regardless of the type of network attached to.Further, UE in the same group can be provided the same DRX profileregardless of the type of network attached to.

In addition to a group identifier, in some embodiments, method 300 canobtain a QCI value associated with the UE (and IMSI). In one embodiment,method 300 can obtain the QCI value during session establishment with apolicy manager such as a PCRF.

In another embodiment, method 300 can alternatively identify a networkslice to assign the UE based on the IMSI value of the UE. In such anembodiment, a corresponding network slice can be determined based on theIMSI, the corresponding network slice being associated with DRXparameters. In this manner, the method 300 can automatically identifyDRX parameters during a network slicing assignment.

In step 306, method 300 can comprise determining at least onediscontinuous reception (DRX) parameter based on the group identifier.

In one embodiment, the DRX parameter can comprise one or both of anidle-mode DRX parameter or a connected mode DRX parameter. In oneembodiment, method 300 can select an idle- or connected-mode DRXparameter based on the RRC state associated with a given UE. In oneembodiment, method 300 can comprise querying a data store of DRXprofiles based on the group identifier. The DRX data store can storeprofiles including DRX parameters for a given group identifier. In oneembodiment, method 300 can retrieve these profiles and provide thecorresponding DRX parameters to the UE.

As one example, method 300 can determine a DRX activity timer valuebased on the group identifier and monitored data of the UE. As usedherein, an activity timer refers to the amount of time before a UEtransitions to an idle state. In one embodiment, a base station candetect inactivity of the UE by monitoring the user plane activity of aUE (e.g., via gNB-CU-User Plane of a gNodeB or packet processingfunction of an eNodeB). In response, the inactivity time is configuredvia the control plane of the base station (e.g., gNB-CU-Control Plane ofa gNodeB or radio control function of an eNodeB) and the data planereceives the inactivity timer value using the UE Inactivity Timer IE. Inone embodiment, the base station can adjust the DRX parameter associatedwith a given group identifier or QCI value based on the per-UEinactivity measurements. Thus, in addition to the group-wise DRXparameters, each UE and each DRX parameter can be adjusted on a per-UEbasis using the above approach.

In step 308, method 300 can comprise transmitting the DRX parameter tothe UE.

In one embodiment, method 300 can comprise transmitting the DRXparameter to the UE via a base station. In response, the base stationtransmits the DRX parameter to the UE via an RRC reconfigurationmessage. In one embodiment, method 300 can alternatively comprisetransmitting the group identifier (and, if applicable, the QCI value) tothe base station, wherein the base station can perform step 306.

FIG. 4 is a block diagram of a cellular network according to someembodiments.

As illustrated, a system 400 includes UE 402 that accesses a datanetwork 408) via an access network 404 and a core network 406. In theillustrated embodiment, UE 402 comprises any computing device capable ofcommunicating with the access network 404. As examples, UE 402 mayinclude mobile phones, smartphones, tablets, laptops, sensors, Internetof Things (IoT) devices, and any other devices equipped with a cellulartransceiver. One example of a UE is provided in FIG. 6 .

In the illustrated embodiment, the access network 404 comprises anetwork allowing over-the-air network communication with UE 402. Ingeneral, the access network 404 includes at least one base station thatis communicatively coupled to the core network 406 and wirelesslycoupled to UE 402.

In one embodiment, the access network 404 comprises a fifth-generation(5G) cellular access network. In one embodiment, the access network 404and UE 402 comprise a NextGen Radio Access Network (NG-RAN). In anembodiment, the access network 404 includes a plurality of nextGeneration Node B (gNodeB) base stations connected to UE 402 via an airinterface. In one embodiment, the air interface comprises a New Radio(NR) air interface. In some embodiments, an NR interface utilizes aCyclic Prefix Orthogonal Frequency-Division Multiple Access (CP-OFDM)downlink modulation scheme and either CP-OFDM or Discrete FourierTransform Spread Orthogonal Frequency Division Multiplexing (DFT-s-OFDM)uplink modulation scheme. In these embodiments, the gNodeB provides allfunctionality to implement and operate the air interface and negotiatesuplinks and downlinks with the UE 402. The gNodeB may additionallyinclude multiple network interfaces for communicating with the corenetwork 406. In one embodiment, the gNodeB includes an interface tocommunicate with a mobility manager (e.g., an AMF) and a secondinterface to communicate with one or more gateway elements in the corenetwork 406, such as an SMF for control data or a UPF for user data. Inone embodiment, the mobility manager manages control plane traffic whilethe gateway elements manage user data traffic, as will be discussed. Insome embodiments, base stations in the access network 404 arecommunicatively connected. For example, in a 5G network, individualgNodeB devices can be communicatively coupled via an X2 interface.

In one embodiment, the access network 404 comprises a fourth-generation(4G) cellular access network. In some embodiments, the access network404 comprises an LTE access network. In one embodiment, the accessnetwork 404 and UE 402 comprise an Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN). In an embodiment, the access network 404 includes a pluralityof Evolved Node B (eNodeB) base stations connected to UE 402 via an airinterface. In one embodiment, the air interface comprises an E-UTRAN Uuor LTE Uu radio air interface. In some embodiments, an E-UTRAN Uuinterface utilizes an orthogonal frequency-division multiple access(OFDMA) downlink modulation scheme and a single-carrierfrequency-division multiple access (SC-FDMA) uplink modulation scheme.In these embodiments, the eNodeB provides all functionality to implementand operate the air interface and negotiates uplinks and downlinks withthe UE 402. The eNodeB may additionally include multiple networkinterfaces for communicating with the core network 406. In oneembodiment, the eNodeB includes an interface to communicate with amobility manager (e.g., a Mobility Management Entity, MME) and a secondinterface to communicate with one or more gateway elements in the corenetwork 406, such as an S-GW or P-GW. In one embodiment, the mobilitymanager manages control plane traffic while the gateway elements manageuser data traffic, as will be discussed. In some embodiments, basestations in the access network 404 are communicatively connected. Forexample, in a 4G network, individual eNodeB devices can becommunicatively coupled, for example, via an X2 interface or any otherinterface.

In some embodiments, the access network 404 may operate in adual-connectivity mode wherein UE 402 connects to multiple base stationsin the access network 404 simultaneously. In some embodiments, dualconnectivity may be implemented via New Radio Dual Connectivity (NR-DC),E-UTRA—NR Dual Connectivity (EN-DC), NG-RAN—E-UTRA-NR Dual Connectivity(NGEN-DC), or NR—E-UTRA Dual Connectivity (NE-DC).

In the illustrated embodiment, the access network 404 provides access toa core network 406 to the UE 402. In the illustrated embodiment, thecore network may be owned and/or operated by a mobile network operator(MNO) and provides wireless connectivity to UE 402. In the illustratedembodiment, this connectivity may comprise voice and data services. Thecore network 406 includes various computing devices, which are describedbriefly herein. Further detail of such devices is provided in FIG. 5 .

At a high level, the core network 406 may include a user plane and acontrol plane. In one embodiment, the control plane comprises networkelements and communications interfaces to allow for the management ofuser connections and sessions. By contrast, the user plane may comprisenetwork elements and communications interfaces to transmit user datafrom UE 402 to elements of the core network 406 and to externalnetwork-attached elements in a data network 408 such as the Internet. Anexample of a control plane function comprises authenticating that a usercan access the core network 406 (i.e., is a subscriber to the MNO). Anexample of a user plane function is the request and receipt of data froman external web server (e.g., via a web browser on a UE). Many otherexamples exist in a 4G or 5G network, and the foregoing examples are notintended to be limiting.

Generally, the core network 406 may include a mobility manager, one ormore gateways (e.g., a serving gateway and packet gateway), and asubscriber database. In practice, the core network 406 may include morecomponents than these. In a 4G network, the mobility manager may beimplemented by an MME, the serving gateway by an S-GW, the packetgateway by a P-GW, and the subscriber database by an HSS. In a 5Gnetwork, the mobility manager may be implemented by an Access MobilityManagement Function (AMF), Session Management Function (SMF), and anAuthentication Server Function (AUSF). Specifically, the AMF performsmobility management while the SMF performs session management, both ofwhich are described herein. Further, the AUSF obtains authenticationvectors from a subscriber database. In a 4G network, the MobilityManagement Entity (MME) performs all these functions. The 4G servinggateway (S-GW) in a 5G network may be implemented by the SMF as well.Specifically, packet routing from the base station to the packet gatewaymay be handled by the SMF in contrast to the S-GW in a 4G network. In a5G network, the packet gateway function user plane may be implemented bythe UPF, which provides packet routing from the serving gateway toexternal services and manages Internet Protocol (IP) address allocationas well as content filtering and blocking. In a 5G network, thesubscriber database may be implemented by a UDR, which stores thesubscriber data. Access to the UDR may be mediated by a UDM, which ispart of the subscriber database, as described herein.

In brief, a UE 402 communicates with the mobility manager toauthenticate and establish a session or bearer with the serving andpacket gateways. The mobility manager accesses the subscriber data toconfirm the UE 402 identity and communicates with the serving gateway toestablish the session. Once established, the UE 402 transmits datarequests through the session to the packet gateway, which manages thetransmitting and receiving data to and from external network services.Specific details of these elements are provided in the followingfigures.

In the illustrated embodiment, the access network 404 and the corenetwork 406 are operated by an MNO. However, in some embodiments,networks 404, 406 may be operated by a private entity and may be closedto public traffic. For example, the components of the core network 406may be provided as a single device, and the access network 404 maycomprise a small form-factor base station. In these embodiments, theoperator of the device can simulate a cellular network, and UE 402 canconnect to this network akin to connecting to a national or regionalnetwork.

FIG. 5 is a block diagram illustrating a cellular network according tosome embodiments.

In the illustrated embodiment, a system 500 includes UE 402communicatively connected to access points 502. As seen in FIG. 5 , theaccess points 502 form an access network such as access network 404. Inone embodiment, the access points 502 and UE 402 comprise a NextGenRadio Access Network (NG-RAN). In an embodiment, access points 502comprise a plurality of gNodeB base stations connected to UE 402 via anair interface. In one embodiment, the air interface comprises a NewRadio (NR) air interface. The gNodeB additionally includes multiplenetwork interfaces for communicating with the core network and,specifically, mobility manager 504 and serving gateway 506. In oneembodiment, the mobility manager 504 in a 5G network comprises an AMF.In one embodiment, the serving gateway 506 comprises an SMF for controldata or UPF for user data.

In another embodiment, access points 502 comprise eNodeB base stationsconnected to UE 402 via an air interface. In some embodiments, the airinterface comprises an E-UTRAN Uu or LTE Uu radio air interface. Inthese embodiments, the eNodeB provides all functionality to implementand operate the air interface and negotiates uplinks and downlinks withthe UE 402. The eNodeB additionally includes multiple network interfacesfor communicating with the core network and, specifically, mobilitymanager 504 and serving gateway 506. In one embodiment, the mobilitymanager 504 comprises an MME in a 4G network. In the illustratedembodiment, solid lines between network elements 504, 506, 508, 510represent user data traffic, while dashed lines between network elements504, 506, 508, 510 represent control or Non-Access Stratum (NAS)traffic.

In the illustrated embodiment, the mobility manager 504 manages controlplane traffic while the gateway elements 506, 510 manage user datatraffic. Specifically, the mobility manager 504 may comprise hardware orsoftware for handling network attachment requests from UE 402. As partof processing these requests, the mobility manager 504 accesses asubscriber database 508. The subscriber database 508 comprises hardwareor software that stores user authorization and authentication data andvalidates users to the network. In some embodiments, the subscriberdatabase 508 may comprise a UDM and UDR in a 5G network. In anotherembodiment, the subscriber database 508 may comprise an HSS in a 4Gnetwork. In one embodiment, the subscriber database 508 may also store alocation of the user updated via a Diameter or similar protocol.

The mobility manager 504 may also be configured to create data sessionsor bearers between UE 402 and serving gateway 506 or gateway 510. In oneembodiment, the serving gateway 506 and gateway 510 may comprise singleor separate devices. In general, the serving gateway 506 routes andforwards user data packets while also acting as the mobility anchor forthe user plane during access point handovers and as the anchor formobility between different network technologies. For idle state UE 402,the serving gateway 506 terminates the downlink data path and triggerspaging when downlink data arrives for the UE 402. The serving gateway506 manages and stores UE 402 contexts, e.g., parameters of the IPbearer service, network internal routing information. In a 5G network,the serving gateway 506 may be implemented by an SMF. In a 4G network,the serving gateway 506 may be implemented by an S-GW.

The serving gateway 506 is communicatively coupled to a gateway 510. Ingeneral, the gateway 510 provides connectivity from the UE 402 toexternal Packet Data Networks (PDNs) such as data network 408 by beingthe point of exit and entry of traffic to external networks (e.g., 408).UE 402 may have simultaneous connectivity with plurality gateways,including gateway 510 for accessing multiple packet data networks. Thegateway 510 performs policy enforcement, packet filtering for each user,charging support, lawful interception, and packet screening. In theillustrated embodiment, gateway 510 also limits access to endpoints suchas an external device 512. In a 5G network, the gateway 510 may beimplemented by a UPF. In a 4G network, the gateway 510 may beimplemented by a P-GW.

In the illustrated embodiment, an external device 512 is communicativelycoupled to the core network via the data network 408. In one embodiment,the data network 408 may comprise the Internet. In the illustratedembodiment, the external device 512, such as an application server, maycomprise any electronic device capable of communicating with the datanetwork 408, and the disclosure is not limited to specific types ofnetwork devices.

FIG. 6 is a block diagram illustrating a computing device showing anexample of a client or server device used in the various embodiments ofthe disclosure.

The computing device 600 may include more or fewer components than thoseshown in FIG. 6 , depending on the deployment or usage of the computingdevice 600. For example, a server computing device, such as arack-mounted server, may not include an audio interface 652, display654, keypad 656, illuminator 658, haptic interface 662, GlobalPositioning System (GPS) receiver such as GPS receiver 664, orcameras/sensors 666. Some devices may include additional components notshown, such as graphics processing unit (GPU) devices, cryptographicco-processors, artificial intelligence (AI) accelerators, or otherperipheral devices.

As shown in the figure, the computing device 600 includes a centralprocessing unit (CPU) 622 in communication with a mass memory 630 via abus 624. The computing device 600 also includes a network interface 650,an audio interface 652, a display 654, a keypad 656, an illuminator 658,an input/output interface (660), a haptic interface 662, a GPS receiver664, and a camera(s) or other optical, thermal, or electromagneticcameras/sensors 666. The computing device 600 can include a plurality ofcameras/sensors 666. The positioning of the cameras/sensors 666 on thecomputing device 600 can change per computing device 600 model, percomputing device 600 capabilities, and the like, or some combinationthereof.

In some embodiments, the CPU 622 may comprise a general-purpose CPU. TheCPU 622 may comprise a single-core or multiple-core CPU. The CPU 622 maycomprise a system-on-a-chip (SoC) or a similar embedded system. In someembodiments, a GPU may be used in place of, or in combination with, aCPU 622. Mass memory 630 may comprise a dynamic random-access memory(DRAM) device, a static random-access memory device (SRAM), or a Flash(e.g., NAND Flash) memory device. In some embodiments, mass memory 630may comprise a combination of such memory types. In one embodiment, thebus 624 may comprise a Peripheral Component Interconnect Express (PCIe)bus. In some embodiments, bus 624 may comprise multiple busses insteadof a single bus.

Mass memory 630 illustrates another example of computer storage mediafor the storage of information such as computer-readable instructions,data structures, program modules, or other data. Mass memory 630 storesa basic input/output system, BIOS 640, for controlling the low-leveloperation of the computing device 600. The mass memory also stores anoperating system 641 for controlling the operation of the computingdevice 600

Applications 642 may include computer-executable instructions which,when executed by the computing device 600, perform any of the methods(or portions of the methods) described previously in the description ofthe preceding Figures. In some embodiments, the software or programsimplementing the method embodiments can be read from a hard disk drive(not illustrated) and temporarily stored in RAM 632 by CPU 622. CPU 622may then read the software or data from RAM 632, process them, and storethem in RAM 632 again.

The computing device 600 may optionally communicate with a base station(not shown) or directly with another computing device. Network interface650 is sometimes known as a transceiver, transceiving device, or networkinterface card (NIC).

The audio interface 652 produces and receives audio signals such as thesound of a human voice. For example, the audio interface 652 may becoupled to a speaker and microphone (not shown) to enabletelecommunication with others or generate an audio acknowledgment forsome action. Display 654 may be a liquid crystal display (LCD), gasplasma, light-emitting diode (LED), or any other type of display usedwith a computing device. Display 654 may also include a touch-sensitivescreen arranged to receive input from an object such as a stylus or adigit from a human hand.

Keypad 656 may comprise any input device arranged to receive input froma user. Illuminator 658 may provide a status indication or providelight.

The computing device 600 also comprises an input/output interface (660)for communicating with external devices, using communicationtechnologies, such as USB, infrared, Bluetooth™, or the like. The hapticinterface 662 provides tactile feedback to a user of the client device.

The GPS receiver 664 can determine the physical coordinates of thecomputing device 600 on the surface of the Earth, which typicallyoutputs a location as latitude and longitude values. GPS receiver 664can also employ other geo-positioning mechanisms, including, but notlimited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA,BSS, or the like, to further determine the physical location of thecomputing device 600 on the surface of the Earth. In one embodiment,however, the computing device 600 may communicate through othercomponents, provide other information that may be employed to determinethe physical location of the device, including, for example, a MACaddress, IP address, or the like.

The present disclosure has been described with reference to theaccompanying drawings, which form a part hereof, and which show, by wayof non-limiting illustration, certain example embodiments. Subjectmatter may, however, be embodied in a variety of different forms and,therefore, covered or claimed subject matter is intended to be construedas not being limited to any example embodiments set forth herein;example embodiments are provided merely to be illustrative. Likewise,the reasonably broad scope for claimed or covered subject matter isintended. Among other things, for example, the subject matter may beembodied as methods, devices, components, or systems. Accordingly,embodiments may, for example, take the form of hardware, software,firmware, or any combination thereof (other than software per se). Thefollowing detailed description is, therefore, not intended to be takenin a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in some embodiments” as used herein does notnecessarily refer to the same embodiment, and the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment. It is intended, for example, that claimed subject matterincludes combinations of example embodiments in whole or in part.

In general, terminology may be understood at least in part from usage incontext. For example, terms such as “and,” “or,” or “and/or,” as usedherein may include a variety of meanings that may depend at least inpart upon the context in which such terms are used. Typically, “or” ifused to associate a list, such as A, B, or C, is intended to mean A, B,and C, here used in the inclusive sense, as well as A, B, or C, hereused in the exclusive sense. In addition, the term “one or more” as usedherein, depending at least in part upon context, may be used to describeany feature, structure, or characteristic in a singular sense or may beused to describe combinations of features, structures, orcharacteristics in a plural sense. Similarly, terms, such as “a,” “an,”or “the,” again, can be understood to convey a singular usage or toconvey a plural usage, depending at least in part upon context. Inaddition, the term “based on” may be understood as not necessarilyintended to convey an exclusive set of factors and may, instead, allowfor the existence of additional factors not necessarily expresslydescribed, again, depending at least in part on context.

The present disclosure has been described with reference to blockdiagrams and operational illustrations of methods and devices. It isunderstood that each block of the block diagrams or operationalillustrations, and combinations of blocks in the block diagrams oroperational illustrations, can be implemented by means of analog ordigital hardware and computer program instructions. These computerprogram instructions can be provided to a processor of a general-purposecomputer to alter its function as detailed herein, a special purposecomputer, ASIC, or other programmable data processing apparatus, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, implement thefunctions/acts specified in the block diagrams or operational block orblocks. In some alternate implementations, the functions/acts noted inthe blocks can occur in different orders than illustrated. For example,two blocks shown in succession can, in fact, be executed substantiallyconcurrently, or the blocks can sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

For the purposes of this disclosure, a non-transitory computer-readablemedium (or computer-readable storage medium/media) stores computer data,which data can include computer program code (or computer-executableinstructions) that is executable by a computer, in machine-readableform. By way of example, and not limitation, a computer-readable mediummay comprise computer-readable storage media for tangible or fixedstorage of data or communication media for transient interpretation ofcode-containing signals. Computer-readable storage media, as usedherein, refers to physical or tangible storage (as opposed to signals)and includes without limitation volatile and non-volatile, removable andnon-removable media implemented in any method or technology for thetangible storage of information such as computer-readable instructions,data structures, program modules or other data. Computer-readablestorage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM,flash memory or other solid-state memory technology, CD-ROM, DVD, orother optical storage, cloud storage, magnetic cassettes, magnetic tape,magnetic disk storage, or other magnetic storage devices, or any otherphysical or material medium which can be used to tangibly store thedesired information or data or instructions and which can be accessed bya computer or processor.

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. However, it willbe evident that various modifications and changes may be made thereto,and additional embodiments may be implemented without departing from thebroader scope of the disclosed embodiments as set forth in the claimsthat follow. The specification and drawings are accordingly to beregarded in an illustrative rather than restrictive sense.

We claim:
 1. A method comprising: receiving a request to attach to acellular network from user equipment (UE); identifying a groupidentifier associated with the UE; determining a discontinuous reception(DRX) parameter based on the group identifier; and transmitting the DRXparameter to the UE.
 2. The method of claim 1, wherein the groupidentifier comprises one of a Subscriber Profile Identifier (SPID) or aSingle Network Slice Selection Assistance Information (S-NSSAI).
 3. Themethod of claim 1, wherein the DRX parameter comprises an idle-mode DRXparameter.
 4. The method of claim 1, further comprising obtaining a QoSClass Identifier (QCI) value associated with the UE.
 5. The method ofclaim 4, wherein determining the DRX parameter comprises determining theDRX parameter based on the group identifier and the QCI value.
 6. Themethod of claim 5, wherein the DRX parameter comprises a connected modeDRX parameter.
 7. The method of claim 1, wherein identifying the groupidentifier associated with the UE comprises mapping a unique identifierof the UE to the group identifier.
 8. A non-transitory computer-readablestorage medium for storing instructions executable by a processor, theinstructions comprising: receiving a request to attach to a cellularnetwork from user equipment (UE); identifying a group identifierassociated with the UE; determining a discontinuous reception (DRX)parameter based on the group identifier; and transmitting the DRXparameter to the UE.
 9. The non-transitory computer-readable storagemedium of claim 8, wherein the group identifier comprises one of aSubscriber Profile Identifier (SPID) or a Single Network Slice SelectionAssistance Information (S-NSSAI).
 10. The non-transitorycomputer-readable storage medium of claim 8, wherein the DRX parametercomprises an idle-mode DRX parameter.
 11. The non-transitorycomputer-readable storage medium of claim 8, further comprisingobtaining a QoS Class Identifier (QCI) value associated with the UE. 12.The non-transitory computer-readable storage medium of claim 11, whereindetermining the DRX parameter comprises determining the DRX parameterbased on the group identifier and the QCI value.
 13. The non-transitorycomputer-readable storage medium of claim 12, wherein the DRX parametercomprises a connected mode DRX parameter.
 14. The non-transitorycomputer-readable storage medium of claim 8, wherein identifying thegroup identifier associated with the UE comprises mapping a uniqueidentifier of the UE to the group identifier.
 15. A device comprising: aprocessor configured to: receiving a request to attach to a cellularnetwork from user equipment (UE); identifying a group identifierassociated with the UE; determining a discontinuous reception (DRX)parameter based on the group identifier; and transmitting the DRXparameter to the UE.
 16. The device of claim 15, wherein the DRXparameter comprises an idle-mode DRX parameter.
 17. The device of claim15, further comprising obtaining a QoS Class Identifier (QCI) valueassociated with the UE.
 18. The device of claim 17, wherein determiningthe DRX parameter comprises determining the DRX parameter based on thegroup identifier and the QCI value.
 19. The device of claim 18, whereinthe DRX parameter comprises a connected mode DRX parameter.
 20. Thedevice of claim 15, wherein identifying the group identifier associatedwith the UE comprises mapping a unique identifier of the UE to the groupidentifier.